1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

If this detection is a false positive, please contact Oleh Vasylenko (@Aldekein) to fix it in the GitGuardian dashboard.

@@             Coverage Diff              @@
##           eip-7702    #1032      +/-   ##
============================================
- Coverage     94.20%   93.42%   -0.78%     
============================================
  Files           156      156              
  Lines         16300    16291       -9     
============================================
- Hits          15355    15220     -135     
- Misses          945     1071     +126     

Flags with carried forward coverage won't be shown. Click here to find out more.

... and 3 files with indirect coverage changes